home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group92c.txt
/
000098_icon-group-sender _Wed Dec 2 10:45:32 1992.msg
< prev
next >
Wrap
Internet Message Format
|
1993-01-04
|
2KB
Received: by cheltenham.cs.arizona.edu; Wed, 2 Dec 1992 12:32:56 MST
Date: Wed, 2 Dec 92 10:45:32 -0700
From: sbw@turing.cse.nau.edu (Steve Wampler)
Message-Id: <9212021745.AA02051@turing.cse.nau.edu>
To: goer@midway.uchicago.edu, icon-group@cs.arizona.edu
Subject: Re: Is a long jump in icon possible ?
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
In article <1992Nov30.200950.16632@midway.uchicago.edu> you write:
|> Frank Kirschner writes:
|> >
|> >Is a long jump in icon possible ?
|>
|> Nope. One thing people periodically complain about is that Icon has
|> no way of handling events (including errors), except perhaps kbhit(),
|> unless you go to the X extensions. I don't know how the X extensions
|> handle errors.
|>
|> I'll bet that a longjump facility won't get into Icon because it would
|> require lots of OS-dependent code. You never know, though. If you
|> have the Icon implementation book, you could take a look to see what
|> would need to be done.
|>
Never, say 'nope'. You *can* do long jumps, after a fashion.
Consider the following approach:
procedure main()
do_work := create A()
if @do_work == "jump" then
# ....
end
procedure A()
B()
end
procedure B()
if erorr_condition then @&main
end
However, this approach has never been formally developed (no guidelines
for how to be systematic about it...
Incidently, I *think* the newer features of Icon (the ability to
trap error conditions do give quite a bit of additional flexibility
in regards to exception handing...